GUILE, GNU's Ubiquitous Intelligent Language for Extension, is a library that implements the Scheme language plus various convenient facilities. It's designed so that you can link it into an application or utility to make it extensible.
guile-1.4: description + notes
Libraries that provide an interpreter for extensibility are not new. But most of them implement ``scripting languages'' that were not designed to be as powerful as a real programming language. GUILE uses Scheme, a powerful yet simple dialect of Lisp. One advantage of GUILE over TCL is that Scheme is a more powerful language. Scheme was designed as a ``programming language'', not as a ``scripting language''. Scheme is also simpler and cleaner than other extension languages such as Perl and Python.
The default subsys are built with dynamic linking enabled and QuickThreads disabled. There are non-default subsys built with QuickThreads enabled. Documentation for guile is still under development, but the Guile Documents page and FAQ are good places to start.
NOTE: Developers intending to use this distribution of libguile for application development should be sure to read the information below. Users installing libguile for the runtime environment only need not read any further.
Developers intending to use this library for development of other freeware packages or their own software applications will need to be familiar with a few peculiarities due to the way that this library is packaged and installed. The reasons for this installation strategy are described further in the fw_common product release notes.
The header files and libraries in this package are installed into /usr/freeware. This means that when building software using this distribution of libguile you should be sure to do the following:
This flag will cause your compilations to correctly find the library's header files at compile time.
- Include the following flag on your compile lines:
- -I/usr/freeware/include
Include the following flag on your link lines:
-L/usr/freeware/lib (if using o32 ABI) -L/usr/freeware/lib32 (if using n32 ABI) -L/usr/freeware/lib64 (if using 64 ABI) This flag will cause the linker to correctly find the library's archive or shared object files at link time.
Additionally, include the following flag on your link lines:
-rpath /usr/freeware/lib (if using o32 ABI) -rpath /usr/freeware/lib32 (if using n32 ABI) -rpath /usr/freeware/lib64 (if using 64 ABI) This flag will allow the binary to locate the shared object library files when the application is run. This is required since the shared objects are stored in these /usr/freeware subdirectories which are not searched by the run-time linker by default.
Finally, if you are building an installable package for inst (contributing to freeware, for example) be sure to make your package depend upon this package. Add the following line to your spec file: prereq ( fw_guile.sw.lib 1230000000 1239999900 ) Following these guidelines will allow your application to safely and easily use the software in this package.
To auto-install this package, go back and click on the respective install icon.